Methods and apparatus for providing map locations in user applications using URL strings

ABSTRACT

Techniques for use in a wireless communication device for displaying a map are described. The device receives via a user interface a selection of a hypertext link object in an electronic file or message. The object is associated with a URL string which includes a server address and location data corresponding to a location. When a mapping application is installed in the device, the device executes the mapping application for rendering a map of the location in response to receiving the selection of the object. When the mapping application is not installed in the device, the device executes a web browser of the device for receiving and displaying a map image of the location in response to receiving the selection of the object.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of and claims priority to U.S.non-provisional patent application having application Ser. No.15/082,480 and a filing date of Mar. 28, 2016, which is a continuationof and claims priority to U.S. non-provisional patent application Ser.No. 14/334,807 and filing date of 18 Jul. 2014, now U.S. Pat. No.9,298,838, which is a continuation of and claim priority to U.S.non-provisional patent application having application Ser. No.13/451,100 and filing date of 19 Apr. 2012, now U.S. Pat. No. 8,788,604,which is a continuation of and claims priority to U.S. non-provisionalpatent application having application Ser. No. 13/150,752 and filingdate of 1 Jun. 2011, now U.S. Pat. No. 8,166,083, which is acontinuation of and claims priority to U.S. non-provisional patentapplication having application Ser. No. 12/781,397 and filing date of 17May 2010, now U.S. Pat. No. 7,970,807, which is a continuation of andclaims priority to U.S. non-provisional patent application havingapplication Ser. No. 11/483,215 and filing date of 7 Jul. 2006, now U.S.Pat. No. 7,720,893, which claims priority to U.S. provisional patentapplication having application No. 60/787,872 and filing date of 31 Mar.2006, and U.S. provisional patent application having application No.60/787,541 and filing date of 31 Mar. 2006, each application beinghereby incorporated by reference herein.

BACKGROUND

Field of the Technology

The present disclosure relates generally to providing map locations inuser applications for the visual display of maps in computer devicesincluding mobile communication devices.

Description of the Related Art

Increasingly, mobile communication devices operating in wirelesscommunication networks are provided with mapping capabilities forpresenting visually displayed maps of geographic locations.Traditionally, visually displayed maps for computer devices have beenlimited to those based on bitmap images which are relatively largefiles. In recent years, newer and even more elaborate mappingcapabilities for computer devices have been devised. Mobilecommunication devices, which typically operate with use of one or morebatteries or battery packs, however, typically have relatively limitedmemory and processing power as compared to larger computer devices suchas personal computers (PCs) or even laptop computers. It is generallydesirable to minimize the use of memory and communication bandwidth(radio bandwidth or otherwise) resources.

Accordingly, there is a need for providing map locations in userapplications for the visual display of maps, especially in mobilecommunication devices which operate in wireless communication networksas well as other computer devices, by fully exploiting the capabilitiesof such devices and minimzing memory and/or communication bandwidthresources where possible.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of present invention will now be described by way of examplewith reference to attached figures, wherein:

FIG. 1 is a block diagram which illustrates pertinent components of amobile communication device and a wireless communication network of acommunication system;

FIG. 2 is a more detailed diagram of a preferred mobile communicationdevice of FIG. 1, namely, a mobile station;

FIG. 3A is a system diagram of network components which provide mappingfunctionality in the mobile communication devices of FIGS. 1 and 2;

FIG. 3B illustrates a message exchange between a mobile communicationdevice and a map server for downloading map content to the mobilecommunication device based on the system of FIG. 3A;

FIG. 3C is a diagram showing a Maplet data structure according to anexemplary embodiment;

FIG. 4 is an illustration of a user interface of the mobilecommunication device;

FIG. 5 is an illustration of various software applications which mayreside in the mobile communication device;

FIGS. 6 and 7 are illustrations of a positioning wheel (one type ofpositioning mechanism) of the mobile communication device;

FIG. 8 is a flowchart which helps describe a method of providing a maplocation in a user application using a Uniform Resource Location (URL)string;

FIG. 9 is a flowchart which helps describe a method of utilizing the maplocation in the user application using the URL string;

FIGS. 10-14 are sequential views of a display of the mobilecommunication device to further illustrate the method of FIG. 8 inconnection with an e-mail application;

FIGS. 15-20 are sequential views of the display to further illustratethe method of FIG. 9 in connection with an e-mail application;

FIGS. 21-24 are sequential views of the display to further illustratethe method of FIG. 8 in connection with any file or message using a COPYfunction and a PASTE function;

FIGS. 25-29 are sequential views of the display to further illustratethe method of FIG. 9 in connection with a tasks application;

FIGS. 30-34 are sequential views of the display to further illustratethe method of FIG. 9 in connection with a map or location application;

FIGS. 35-43 are sequential views of the display to further illustratethe method of FIG. 9 in connection with a calendar application;

FIG. 44 is a flowchart which describes a method of processing the URLstring in accordance with the present disclosure; and

FIG. 45 is a system diagram of network components for use with themethod of FIG. 44.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Methods and apparatus for use in mapping a location in a computer deviceare described herein. In one illustrative example, the method includesthe steps of receiving an electronic file or message which includes ahypertext link mapping indicator associated with a uniform resourcelocator (URL) string having a server address and latitude and longitudecoordinates; receiving, through a user interface of the computer device,an end user selection of the hypertext link mapping indicator in theelectronic file or message; and in response to the end user selection ofthe hypertext link mapping indicator: if a predetermined type of mappingapplication is provided in the computer device, invoking a mappingfunction of the mapping application to produce a map of a locationcorresponding to the latitude and longitude coordinates for visualdisplay in a display of the computer device (e.g. based on receivedmaplet data); and if the predetermined type of mapping application typeis not provided in the computer device, requesting and receiving mapdata from a map coordinating server identified by the server address ofthe URL string to produce a map of the location for visual display inthe display (e.g. based on a bitmap image). If the predetermined type ofmapping application is not provided in the computer device, and thecomputer device or associated browser is identified as not being that ofa mobile communication device (i.e. the computer device has higherprocessing capabilities), then the computer device causes a request tobe sent to the map coordinating server at the server address and, inresponse to the request, receives a redirection from the mapcoordinating server to an interactive map server at an interactive mapserver address and further requests and receives map data from theinteractive map server at the interactive map server address to producea map of the location for visual display in the display. Advantageously,processing of the received hypertext link mapping indicator is handleddifferently depending on the type of device or whether a predeterminedmapping application is installed in the device, so that optimal mappingfunctionality is provided for different device environments.

FIG. 1 is a block diagram of a communication system 100 which includes amobile station 102 (one type of wireless or mobile communication device)which communicates through a wireless communication network 104. Mobilestation 102 preferably includes a visual display 112, a keyboard 114,and perhaps one or more auxiliary user interfaces (UI) 116, each ofwhich are coupled to a controller 106. Controller 106 is also coupled toradio frequency (RF) transceiver circuitry 108 and an antenna 110.Typically, controller 106 is embodied as a central processing unit (CPU)which runs operating system software in a memory component (not shown).Controller 106 will normally control overall operation of mobile station102, whereas signal processing operations associated with communicationfunctions are typically performed in RF transceiver circuitry 108.Controller 106 interfaces with device display 112 to display receivedinformation, stored information, user inputs, and the like. Keyboard114, which may be a telephone type keypad or full alphanumeric keyboard,is normally provided for entering data for storage in mobile station102, information for transmission to network 104, a telephone number toplace a telephone call, commands to be executed on mobile station 102,and possibly other or different user inputs.

Mobile station 102 sends communication signals to and receivescommunication signals from network 104 over a wireless link via antenna110. RF transceiver circuitry 108 performs functions similar to those ofstation 118 and BSC 120, including for example modulation/demodulationand possibly encoding/decoding and encryption/decryption. It is alsocontemplated that RF transceiver circuitry 108 may perform certainfunctions in addition to those performed by BSC 120. It will be apparentto those skilled in art that RF transceiver circuitry 108 will beadapted to particular wireless network or networks in which mobilestation 102 is intended to operate.

Mobile station 102 includes a battery interface 134 for receiving one ormore rechargeable batteries 132. Battery 132 provides electrical powerto electrical circuitry in mobile station 102, and battery interface 134provides for a mechanical and electrical connection for battery 132.Battery interface 134 is coupled to a regulator 136 which regulatespower to the device. When mobile station 102 is fully operational, an RFtransmitter of RF transceiver circuitry 108 is typically keyed or turnedon only when it is sending to network, and is otherwise turned off toconserve resources. Similarly, an RF receiver of RF transceivercircuitry 108 is typically periodically turned off to conserve poweruntil it is needed to receive signals or information (if at all) duringdesignated time periods.

Mobile station 102 operates using a Subscriber Identity Module (SIM) 140which is connected to or inserted in mobile station 102 at a SIMinterface 142. SIM 140 is one type of a conventional “smart card” usedto identify an end user (or subscriber) of mobile station 102 and topersonalize the device, among other things. Without SIM 140, the mobilestation terminal is not fully operational for communication throughwireless network 104. By inserting SIM 140 into mobile station 102, anend user can have access to any and all of his/her subscribed services.SIM 140 generally includes a processor and memory for storinginformation. Since SIM 140 is coupled to SIM interface 142, it iscoupled to controller 106 through communication lines 144. In order toidentify the subscriber, SIM 140 contains some user parameters such asan International Mobile Subscriber Identity (IMSI). An advantage ofusing SIM 140 is that end users are not necessarily bound by any singlephysical mobile station. SIM 140 may store additional user informationfor the mobile station as well, including datebook (or calendar)information and recent call information.

Mobile station 102 may consist of a single unit, such as a datacommunication device, a cellular telephone, a Global Positioning System(GPS) unit, a multiple-function communication device with data and voicecommunication capabilities, a personal digital assistant (PDA) enabledfor wireless communication, or a computer incorporating an internalmodem. Alternatively, mobile station 102 may be a multiple-module unitcomprising a plurality of separate components, including but in no waylimited to a computer or other device connected to a wireless modem. Inparticular, for example, in the mobile station block diagram of FIG. 1,RF transceiver circuitry 108 and antenna 110 may be implemented as aradio modem unit that may be inserted into a port on a laptop computer.In this case, the laptop computer would include display 112, keyboard114, one or more auxiliary UIs 116, and controller 106 embodied as thecomputer's CPU. It is also contemplated that a computer or otherequipment not normally capable of wireless communication may be adaptedto connect to and effectively assume control of RF transceiver circuitry108 and antenna 110 of a single-unit device such as one of thosedescribed above. Such a mobile station 102 may have a more particularimplementation as described later in relation to mobile station 402 ofFIG. 2.

Mobile station 102 communicates in and through wireless communicationnetwork 104. Wireless communication network 104 may be a cellulartelecommunications network. In the embodiment of FIG. 1, wirelessnetwork 104 is configured in accordance with Global Systems for MobileCommunications (GSM) and General Packet Radio Service (GPRS)technologies. Although wireless communication network 104 is describedherein as a GSM/GPRS type network, any suitable network technologies maybe utilized such as Code Division Multiple Access (CDMA), Wideband CDMA(WCDMA), whether 2G, 3G, or Universal Mobile Telecommunication System(UMTS) based technologies. In this embodiment, the GSM/GPRS wirelessnetwork 104 includes a base station controller (BSC) 120 with anassociated tower station 118, a Mobile Switching Center (MSC) 122, aHome Location Register (HLR) 132, a Serving General Packet Radio Service(GPRS) Support Node (SGSN) 126, and a Gateway GPRS Support Node (GGSN)128. MSC 122 is coupled to BSC 120 and to a landline network, such as aPublic Switched Telephone Network (PSTN) 124. SGSN 126 is coupled to BSC120 and to GGSN 128, which is in turn coupled to a public or privatedata network 130 (such as the Internet). HLR 132 is coupled to MSC 122,SGSN 126, and GGSN 128.

Station 118 is a fixed transceiver station, and station 118 and BSC 120may be referred to as transceiver equipment. The transceiver equipmentprovides wireless network coverage for a particular coverage areacommonly referred to as a “cell”. The transceiver equipment transmitscommunication signals to and receives communication signals from mobilestations within its cell via station 118. The transceiver equipmentnormally performs such functions as modulation and possibly encodingand/or encryption of signals to be transmitted to the mobile station inaccordance with particular, usually predetermined, communicationprotocols and parameters, under control of its controller. Thetransceiver equipment similarly demodulates and possibly decodes anddecrypts, if necessary, any communication signals received from mobilestation 102 within its cell. Communication protocols and parameters mayvary between different networks. For example, one network may employ adifferent modulation scheme and operate at different frequencies thanother networks.

The wireless link shown in communication system 100 of FIG. 1 representsone or more different channels, typically different radio frequency (RF)channels, and associated protocols used between wireless network 104 andmobile station 102. An RF channel is a limited resource that must beconserved, typically due to limits in overall bandwidth and a limitedbattery power of mobile station 102. Those skilled in art willappreciate that a wireless network in actual practice may includehundreds of cells, each served by a station 118 (i.e. or stationsector), depending upon desired overall expanse of network coverage. Allpertinent components may be connected by multiple switches and routers(not shown), controlled by multiple network controllers.

For all mobile station's 102 registered with a network operator,permanent data (such as mobile station 102 user's profile) as well astemporary data (such as mobile station's 102 current location) arestored in HLR 132. In case of a voice call to mobile station 102, HLR132 is queried to determine the current location of mobile station 102.A Visitor Location Register (VLR) of MSC 122 is responsible for a groupof location areas and stores the data of those mobile stations that arecurrently in its area of responsibility. This includes parts of thepermanent mobile station data that have been transmitted from HLR 132 tothe VLR for faster access. However, the VLR of MSC 122 may also assignand store local data, such as temporary identifications. Optionally, theVLR of MSC 122 can be enhanced for more efficient co-ordination of GPRSand non-GPRS services and functionality (e.g. paging forcircuit-switched calls which can be performed more efficiently via SGSN126, and combined GPRS and non-GPRS location updates).

Serving GPRS Support Node (SGSN) 126 is at the same hierarchical levelas MSC 122 and keeps track of the individual locations of mobilestations. SGSN 126 also performs security functions and access control.Gateway GPRS Support Node (GGSN) 128 provides interworking with externalpacket-switched networks and is connected with SGSNs (such as SGSN 126)via an IP-based GPRS backbone network. SGSN 126 performs authenticationand cipher setting procedures based on the same algorithms, keys, andcriteria as in existing GSM. In conventional operation, cell selectionmay be performed autonomously by mobile station 102 or by thetransceiver equipment instructing mobile station 102 to select aparticular cell. Mobile station 102 informs wireless network 104 when itreselects another cell or group of cells, known as a routing area.

In order to access GPRS services, mobile station 102 first makes itspresence known to wireless network 104 by performing what is known as aGPRS “attach”. This operation establishes a logical link between mobilestation 102 and SGSN 126 and makes mobile station 102 available toreceive, for example, pages via SGSN, notifications of incoming GPRSdata, or SMS messages over GPRS. In order to send and receive GPRS data,mobile station 102 assists in activating the packet data address that itwants to use. This operation makes mobile station 102 known to GGSN 128;interworking with external data networks can thereafter commence. Userdata may be transferred transparently between mobile station 102 and theexternal data networks using, for example, encapsulation and tunneling.Data packets are equipped with GPRS-specific protocol information andtransferred between mobile station 102 and GGSN 128.

Those skilled in art will appreciate that a wireless network may beconnected to other systems, possibly including other networks, notexplicitly shown in FIG. 1. A network will normally be transmitting atvery least some sort of paging and system information on an ongoingbasis, even if there is no actual packet data exchanged. Although thenetwork consists of many parts, these parts all work together to resultin certain behaviours at the wireless link.

FIG. 2 is a detailed block diagram of a preferred mobile station 202 ofthe present disclosure. Mobile station 202 is preferably a two-waycommunication device having at least voice and advanced datacommunication capabilities, including the capability to communicate withother computer systems. Depending on the functionality provided bymobile station 202, it may be referred to as a data messaging device, atwo-way pager, a cellular telephone with data messaging capabilities, awireless Internet appliance, or a data communication device (with orwithout telephony capabilities). Mobile station 202 may communicate withany one of a plurality of fixed transceiver stations 200 within itsgeographic coverage area.

Mobile station 202 will normally incorporate a communication subsystem211, which includes a receiver 212, a transmitter 214, and associatedcomponents, such as one or more (preferably embedded or internal)antenna elements 216 and 218, local oscillators (LOs) 213, and aprocessing module such as a digital signal processor (DSP) 220.Communication subsystem 211 is analogous to RF transceiver circuitry 108and antenna 110 shown in FIG. 1. As will be apparent to those skilled infield of communications, particular design of communication subsystem211 depends on the communication network in which mobile station 202 isintended to operate.

Mobile station 202 may send and receive communication signals over thenetwork after required network registration or activation procedureshave been completed. Signals received by antenna 216 through the networkare input to receiver 212, which may perform such common receiverfunctions as signal amplification, frequency down conversion, filtering,channel selection, and like, and in example shown in FIG. 2,analog-to-digital (A/D) conversion. A/D conversion of a received signalallows more complex communication functions such as demodulation anddecoding to be performed in DSP 220. In a similar manner, signals to betransmitted are processed, including modulation and encoding, forexample, by DSP 220. These DSP-processed signals are input totransmitter 214 for digital-to-analog (D/A) conversion, frequency upconversion, filtering, amplification and transmission over communicationnetwork via antenna 218. DSP 220 not only processes communicationsignals, but also provides for receiver and transmitter control. Forexample, the gains applied to communication signals in receiver 212 andtransmitter 214 may be adaptively controlled through automatic gaincontrol algorithms implemented in DSP 220.

Network access is associated with a subscriber or user of mobile station202, and therefore mobile station 202 requires a Subscriber IdentityModule or “SIM” card 262 to be inserted in a SIM interface 264 in orderto operate in the network. SIM 262 includes those features described inrelation to FIG. 1. Mobile station 202 is a battery-powered device so italso includes a battery interface 254 for receiving one or morerechargeable batteries 256. Such a battery 256 provides electrical powerto most if not all electrical circuitry in mobile station 202, andbattery interface 254 provides for a mechanical and electricalconnection for it. The battery interface 254 is coupled to a regulator(not shown) which provides a regulated voltage V to all of thecircuitry.

Mobile station 202 includes a microprocessor 238 (which is oneimplementation of controller 106 of FIG. 1) which controls overalloperation of mobile station 202. Communication functions, including atleast data and voice communications, are performed through communicationsubsystem 211. Microprocessor 238 also interacts with additional devicesubsystems such as a display 222, a flash memory 224, a random accessmemory (RAM) 226, auxiliary input/output (I/O) subsystems 228, a serialport 230, a keyboard 232, a speaker 234, a microphone 236, a short-rangecommunications subsystem 240, and any other device subsystems generallydesignated at 242. Some of the subsystems shown in FIG. 2 performcommunication-related functions, whereas other subsystems may provide“resident” or on-device functions. Notably, some subsystems, such askeyboard 232 and display 222, for example, may be used for bothcommunication-related functions, such as entering a text message fortransmission over a communication network, and device-resident functionssuch as a calculator or task list. Operating system software used bymicroprocessor 238 is preferably stored in a persistent store such asflash memory 224, which may alternatively be a read-only memory (ROM) orsimilar storage element (not shown). Those skilled in the art willappreciate that the operating system, specific device applications, orparts thereof, may be temporarily loaded into a volatile store such asRAM 226.

Microprocessor 238, in addition to its operating system functions,preferably enables execution of software applications on mobile station202. A predetermined set of applications which control basic deviceoperations, including at least data and voice communicationapplications, as well as techniques of the present disclosure, willnormally be installed on mobile station 202 during its manufacture. Apreferred application that may be loaded onto mobile station 202 may bea personal information manager (PIM) application having the ability toorganize and manage data items relating to user such as, but not limitedto, e-mail, calendar events, voice mails, appointments, and task items.Naturally, one or more memory stores are available on mobile station 202and SIM 256 to facilitate storage of PIM data items and otherinformation.

The PIM application preferably has the ability to send and receive dataitems via the wireless network. In the present disclosure, PIM dataitems are seamlessly integrated, synchronized, and updated via thewireless network, with the mobile station user's corresponding dataitems stored and/or associated with a host computer system therebycreating a mirrored host computer on mobile station 202 with respect tosuch items. This is especially advantageous where the host computersystem is the mobile station user's office computer system. Additionalapplications may also be loaded onto mobile station 202 through network,an auxiliary I/O subsystem 228, serial port 230, short-rangecommunications subsystem 240, or any other suitable subsystem 242, andinstalled by a user in RAM 226 or preferably a non-volatile store (notshown) for execution by microprocessor 238. Such flexibility inapplication installation increases the functionality of mobile station202 and may provide enhanced on-device functions, communication-relatedfunctions, or both. For example, secure communication applications mayenable electronic commerce functions and other such financialtransactions to be performed using mobile station 202.

In a data communication mode, a received signal such as a text message,an e-mail message, or web page download will be processed bycommunication subsystem 211 and input to microprocessor 238.Microprocessor 238 will preferably further process the signal for outputto display 222 or alternatively to auxiliary I/O device 228. A user ofmobile station 202 may also compose data items, such as e-mail messages,for example, using keyboard 232 in conjunction with display 222 andpossibly auxiliary I/O device 228. Keyboard 232 is preferably a completealphanumeric keyboard and/or telephone-type keypad. These composed itemsmay be transmitted over a communication network through communicationsubsystem 211.

For voice communications, the overall operation of mobile station 202 issubstantially similar, except that the received signals would be outputto speaker 234 and signals for transmission would be generated bymicrophone 236. Alternative voice or audio I/O subsystems, such as avoice message recording subsystem, may also be implemented on mobilestation 202. Although voice or audio signal output is preferablyaccomplished primarily through speaker 234, display 222 may also be usedto provide an indication of the identity of a calling party, duration ofa voice call, or other voice call related information, as some examples.

Serial port 230 in FIG. 2 is normally implemented in a personal digitalassistant (PDA)-type communication device for which synchronization witha user's desktop computer is a desirable, albeit optional, component.Serial port 230 enables a user to set preferences through an externaldevice or software application and extends the capabilities of mobilestation 202 by providing for information or software downloads to mobilestation 202 other than through a wireless communication network. Thealternate download path may, for example, be used to load an encryptionkey onto mobile station 202 through a direct and thus reliable andtrusted connection to thereby provide secure device communication.

Short-range communications subsystem 240 of FIG. 2 is an additionaloptional component which provides for communication between mobilestation 202 and different systems or devices, which need not necessarilybe similar devices. For example, subsystem 240 may include an infrareddevice and associated circuits and components, or a Bluetooth™communication module to provide for communication with similarly-enabledsystems and devices. Bluetooth™ is a registered trademark of BluetoothSIG, Inc.

FIG. 3A is a system diagram of network components which provide mappingfunctionality in the mobile communication devices of FIGS. 1 and 2. Toachieve this, a mapping application is also provided in memory of themobile communication device (e.g. a mapping application 550 of FIG. 5)for rendering of visual maps in its display. Mobile communicationdevices, such as mobile station 202, are connected over a mobile carriernetwork 303, for communication through a firewall 305 to a relay 307. Arequest for map data from any one of the mobile communication devices isreceived at relay 307 and passed via a secure channel 309 throughfirewall 311 to a corporate enterprise server 313 and corporate mobiledata system (MDS) server 315. The request is then passed via firewall317 to a public location-based service (LBS) server 321 which provideslocation-based services (LBS) to handle the request. The network mayinclude a plurality of such LBS servers where requests are distributedand processed through a load distributing server. The LBS data may bestored on this network server 321 in a network database 322, or may bestored on a separate LBS data server (not shown). Private corporate datastored on corporate LBS server 325 may be added to the public data viacorporate MDS server 315 on the secure return path to mobile station202. Alternatively, where no corporate servers provided, the requestfrom mobile station 202 may be passed via relay 307 to a public MDSserver 327, which sends the request to public LBS server 321 providingLBS to handle the request.

A Maplet data structure is provided that contains all of the graphic andlabeled content associated with a geographic area (e.g. map featuressuch as restaurants (point features), streets (line features), or lakes(polygon features)). Maplets are structured in Layers of “DEntries”(Data Entries) identified by a “Layer ID” to enable data from differentsources to be deployed to the device and meshed for proper rendering.Each DEntry is representative of one or more artifact or label (or acombination of both) and includes coordinate information (also referredto a “bounding box” or “bounding area”) to identify the area covered bythe DEntry and a plurality of data Points that together represent theartifact or label. For example, a DEntry may be used to represent astreet on a city map (or a plurality of streets), wherein the variousPoints within the DEntry are separated into different parts representingvarious portions of the artifact (e.g. portions of a street). A mobiledevice may issue a request for the map server to download only thoseDEntries that are included within a specified area or bounding boxrepresenting an area of interest that can be represented by, forexample, a pair of bottom left, top right coordinates.

As discussed later below with reference to FIG. 3B, the mobile deviceissues one or more AOI (Area of Interest) requests, DEntry or datarequests and Maplet Index requests to the map server, for selectivedownloading of map data based on user context Thus, rather thantransmitting the entire map data with each request from the device,local caching may be used within the mobile device in conjunction withcontext filtering of map data on the server. For example, if a user'smobile device is GPS enabled and the user is traveling in an automobileat 120 km/hr along a freeway then context filtering can be employed toprevent downloading of map data relating to passing side streets. Or, ifthe user is traveling in an airplane at 30,000′ then context filteringcan be employed to prevent downloading of map data for any streetswhatsoever. Also, a user's context can be defined, for example, in termsof occupation (e.g. a user whose occupation is transport truck drivercan employ context filtering to prevent downloading of map data for sidestreets on which the user's truck is incapable of traveling, or a userwhose occupation is to replenish supplies of soft drink dispensingmachines can employ context filtering to download public map datashowing the user's geographical area of responsibility with irrelevantfeatures such as lakes or parks filtered out and private map datacontaining the location of soft drink dispensing machines superimposedon the public map data.

The Maplet Index request results in a Maplet Index (i.e. only a portionof the Maplet that provides a table of contents of the map dataavailable within the Maplet rather than the entire Maplet) beingdownloaded from the map server to the device, thereby conserving OTA(Over-the-Air) bandwidth and device memory caching requirements. TheMaplet Index conforms to the same data structure as a Maplet, but omitsthe data Points. Consequently, the Maplet Index is small (e.g. 300-400bytes) relative to the size of a fully populated Maplet or aconventional bit map, and includes DEntry bounding boxes and attributes(size, complexity, etc.) for all artifacts within the Maplet. As thefield of view changes (e.g. for a location-aware device that displays amap while moving), the device (client) software assesses whether or notit needs to download additional data from the server. Thus, as discussedabove, if the size attribute or complexity attribute of an artifact thathas started to move into the field of view of the device (but is not yetbeing displayed) is not relevant to the viewer's current context, thenthe device can choose not to display that portion of the artifact. Onthe other hand, if the portion of the artifact is appropriate fordisplay then the device accesses its cache to determine whether theDEntries associated with that portion of the artifact have already beendownloaded, in which case the cached content is displayed. Otherwise,the device issues a request for the map server to download all of theDEntries associated with the artifact portion.

By organizing the Maplet data structure in Layers, it is possible toseamlessly combine and display information obtained from public andprivate databases. For example, it is possible for the device to displayan office building at a certain address on a street (e.g. 1st z-orderattribute from public database), adjacent a river (e.g. 2^(nd) z-orderattribute from public database), with a superimposed floor plan of thebuilding to show individual offices (e.g. 11^(th) z-order attribute froma private database, accessible through a firewall).

Referring back to FIG. 3A, within the network having LBS server(s) 321and database(s) 322 accessible to it, all of the map data for the entireworld is divided and stored as a grid according to various levels ofresolution (zoom), as set forth below in Table A. Thus, a single A levelMaplet represents a 0.05×0.05 degree grid area; a single B level Mapletrepresents a 0.5×0.5 degree grid area; a single C level Mapletrepresents a 5×5 degree grid area; a single D level Maplet represents a50×50 degree grid area and a single E level Maplet represents the entireworld in a single Maplet. It is understood that Table A is only anexample of a particular Maplet grid configuration; other or differentgrid configurations may also be developed. A Maplet comprises of a setof layers, with each layer containing a set of DEntries, and eachDEentry containing a set of points.

TABLE A # of Maplets # of Maplets # of Maplets Grid to cover to cover tocover Level (degrees) the World North America Europe A 0.05 × 0.0525,920,000 356,000 100,000 B 0.5 × 0.5 259,200 6,500 1000 C 5 × 5 2,59296 10 D 50 × 50 32 5 5 E World 1 1 1

Turning now to FIG. 3B, three specific types of requests may begenerated by a mobile communication device (i.e. the client)—AOIrequests, DEntry requests, and Maplet Index requests. The requests maybe generated separately or in various combinations, as discussed ingreater detail below. An AOI (area of interest) request calls for allDEntries in a given area (bounding box) for a predetermined or selectedset of z-order layers. The AOI request is usually generated when themobile communication device moves to a new area so as to fetch Dentriesfor display before the device client knows what is available in theMaplet. The Maplet Index has the exact same structure as a Maplet butdoes not contain complete DEntries (i.e. the data Points that actuallyrepresent artifacts and labels are omitted). Thus, a Maplet Indexdefines what layers and DEntries are available for a given Maplet. Adata or DEntry request is a mechanism to bundle together all of therequired DEntries for a given Maplet.

Typically, AOI and Maplet Index requests are paired together in the samemessage, although they need not be, while DEntry requests are generatedmost often. For example, when the mobile communication device moves intoan area in connection with which no information has been stored on thedevice client, the Maplet Index request returns a Maplet Index thatindicates what data the client can specifically request from the server321, while the AOI request returns any DEntries within the area ofinterest for the specified layers (if they exist). In the examplerequests shown in FIG. 3B, the desired Maplet is identified within aDEntry request by specifying the bottom-left Maplet coordinate. Inaddition, the DEntry request may include a layer mask so that unwantedLayers are not downloaded, a DEntry mask so that unwanted data Pointsare not downloaded, and zoom values to specify a zoom level for therequested DEntry. Once the device client has received the requestedMaplet Index, the client typically then issues multiple DEntry requeststo ask for specific DEntries (since the client knows all of the specificDEntries that are available based on the Maplet Index).

According to the present disclosure herein, a collection of 20×20A-level Maplets (representing a 1×1 degree square) is compiled into aMaplet file (.mbl). An .mbl file contains a header which specifies theoffset and length of each Maplet in the .mbl file. The same 20×20collection of Maplet index data is compiled into a Maplet Index file(.mbx). The .mbl and .mbx file structures are set forth in Tables B andC, respectively.

TABLE B Address Offset Offset Length 0x000 Maplet # 0 Offset Maplet # 0Length (4 bytes) (4 bytes) 0x008 Maplet # 1 Offset Maplet # 1 Length0x010 Maplet # 2 Offset Maplet # 2 Length . . . . . . . . . 0xC78 Maplet# 399 Maplet # 399 Offset Length 0xC80 Beginning of Maplet # 0 0xC80 +Size of Maplet # 0 Beginning of Maplet # 1 0xC80 + Size of Maplet # 0 +Beginning of Maplet # 2 # 1 . . . . . . 0xC80 + Σ of Size of MapletsBeginning of Maplet # 399 (# 0: # 398)

In Table B, the offset of Maplet #0 is 0x0000_0000 since, according tothe present disclosure, the data structure is based on the assumptionthat the base address for the actual Maplet data is 0x0000_0C80.Therefore the absolute address for Maplet #0 data is: Maplet #0Address=Base Address (0x0000_0C80)+Maplet #0 Offset (0x0000_0000), andadditional Maplet addresses are calculated as: Maplet # (n+1)Offset=Maplet # (n) Offset+Maplet #(n) Length. If a Maplet has no dataor does not exist, the length parameter is set to zero (0x0000_0000).

TABLE C Offset (4 Length (4 Address Offset bytes) bytes) 0x000 MapletIndex Maplet Index # 0 Offset # 0 Length 0x008 Maplet Index Maplet Index# 1 Offset # 1 Length 0x010 Maplet Index Maplet Index # 2 Offset # 2Length . . . . . . . . . 0xC78 Maplet Index Maplet Index # 399 Offset #399 Length 0xC80 Beginning of Maplet Index # 0 0xC80 + Size of MapletBeginning of Maplet Index # 1 Index # 0 0xC80 + Size of Maplet Beginningof Maplet Index # 2 Index # 0 + # 1 . . . . . . 0xC80 + Σ of Size ofMaplet Beginning of Maplet Index # 399 Indices (# 0: # 399)

In Table C, the offset of Maplet Index #0 is 0x0000_0000 since,according to the present disclosure the data structure is based on theassumption that the base address for the actual Maplet index data is0x0000_0C80. Therefore the absolute address for Maplet Index #0 data is:Maplet Index #0 Address=Base Address (0x0000_0C80)+Maplet Index #0Offset (0x0000_0000), and additional Maplet index addresses arecalculated as: Maplet Index # (n+1) Offset=Maplet Index # (n)Offset+Maplet Index #(n) Length. If a Maplet Index has no data or doesnot exist, the length parameter is set to zero (0x0000_0000).

FIG. 3C and Table D below, in combination, illustrate an exemplaryembodiment of a basic Maplet data structure. Generally, as noted above,the Maplet data structure can be said to include a Maplet Index (ie anindex of the DEntries, each of which representative of either anartifact or a label or both) together with data Points for each DEntrythat actually form such artifacts and labels. In this example, eachMaplet includes a Map ID (e.g. 0xA1B1C1D1), the # of Layers in theMaplet, and a Layer Entry for each Layer. The Map ID identifies the dataas a valid Maplet, and according to one alternative, may also be used toidentify a version number for the data. The # of Layers is an integerwhich indicates the number of Layers (and therefore Layer Entries) inthe Maplet. Each Layer Entry defines rendering attributes for allDEntries in the corresponding Layer and is followed by a list ofDEntries for that Layer. The above forms a Maplet Index. For a completeMaplet, each DEntry contains a set of data Points (referred to herein asoPoints) or Labels). Note that Layers may have multiple DEntries and thecomplete list of DEntrys and Points are grouped by Layer and separatedby a Layer Separator (e.g. hex value 0xEEEEEEEE). According to anexemplary embodiment, each Layer Entry is 20 bytes long, and a DEntry is12 bytes long. However, the number of Layers, number of DEntries perLayer and the number of Points per DEntry depends on the map data and isvariable.

Table D provides a high “byte-level” description of a Maplet.

TABLE D Data Quantity Total # of Bytes Map ID 1 4 bytes # of Layers 1 4bytes Layer Entrys # of Layers 20 bytes × (# of Layers) DEntry of a x (#of # of Layers 12 bytes × (Σ of the # of Layer DEntries DEntrys in eachLayer) + Points for in a 4 bytes × (Σ of the # of DEntry of a Layer)Points in each DEntry in Layer each Layer) + Layer Separator 4 bytes ×(# of Layers)

For even greater detail if desired, this application hereby incorporatesby reference herein a U.S. provisional patent application entitled“Method And System For Distribution Of Map Content To MobileCommunication Devices” having Ser. No. 60/787,541, lead inventor EricJohnson, and a filing date of 31 Mar. 2006.

FIG. 4 is an example of a user interface 402 of mobile station 202 whichincludes at least display 222, keyboard 232, speaker 234, microphone236, and a cursor or view positioning mechanism such as a positioningwheel 410 (e.g. a scrollwheel wheel) or a trackball 433. Although shownenlarged in FIG. 4 for clarity, this mobile station 202 is sized to be ahandheld portable device. As an alternative to or in addition topositioning wheel 410 and/or trackball 433, a wide range of one or morepointing or cursor/view positioning mechanisms such as a touch pad ajoystick button, a mouse, a touchscreen, a tablet, or other whetherpresently known or unknown, may be employed. As employed herein, theterm “cursor” shall expressly include, but not be limited by, a pointer,a movable item or other visual cue (e.g., without limitation, agraphical object; a special symbol; an outline; a rectangle; anunderline character; a blinking item) used to mark a position or pointto another item on a display, in order to, for example, indicateposition for data entry or for selection of the other item.

Keys 428 of keyboard 232 are disposed on a front face of a housing 406and positioning wheel 410 is disposed at a side of housing 406. Keyboard232 is in the example form of a reduced QWERTY keyboard including aplurality of keys 428 that serve as input members. It can be seen thatthe arrangement of the characters 448 on keys 428 of keyboard 424 isgenerally of the QWERTY arrangement, albeit with many of keys 428including two of characters 448. In the example depiction of keyboard424, many of keys 428 include two characters, such as including a firstcharacter 452 and a second character 456 assigned thereto. It isunderstood that the expression “characters” shall broadly be construedto include letters, digits, symbols and the like and can additionallyinclude ideographic characters, components thereof, and the like. One ofkeys 428 of keyboard 424 includes as the characters 448 thereof theletters “Q” and “W”, and an adjacent key 428 includes as the characters448 thereof the letters “E” and “R”. Keyboard 424 may be of otherconfigurations, such as an AZERTY keyboard, a QWERTZ keyboard, a Dvorakkeyboard, or other keyboard or keypad arrangement, whether presentlyknown or unknown, and either reduced or not reduced (i.e. full). In a“full” or non-reduced keyboard or keypad arrangement, each key has asingle letter (not multiple letters) of the alphabet assigned to it.

Among keys 428 of keyboard 232 are a <NEXT> key 440 and an <ENTER> key444. The <NEXT> key 440, wherein, for example, “<NEXT>” may be a symbolor may be the word “next” provided (e.g. printed) on the key, may bepressed to provide a selection input to the processor and providessubstantially the same selection input as is provided by a rotationalinput of positioning wheel 410. Since <NEXT> key 440 is providedadjacent a number of other keys 428 of keyboard 232, the user canprovide a selection input to the processor substantially without movingthe user's hands away from the keyboard 232 during a text entryoperation. Another key, the <ESC> key 445 is disposed on the side ofhousing 406 adjacent positioning wheel 438, although the same or similarkey may be disposed as part of keyboard 232. Among keys 428 of thekeyboard 424 additionally is a <DEL> key 486 that can be provided todelete a text entry.

Positioning wheel 410 may serve as another input member and is bothrotatable, as is indicated by an arrow 412, to provide selection inputsto the processor, and also can be pressed in a direction generallytoward housing 406, as is indicated by an arrow 414 to provide anotherselection input to the processor. Positioning wheel 410 will bedescribed in more detail in relation to FIGS. 6 and 7 below.

Display 222 may include a cursor 484 that depicts generally where thenext input or selection from user interface 402 will be received.Display 222 is shown in FIG. 4 as displaying a home screen thatrepresents a number of applications 586 (see also FIG. 5 which showssome of the example possible applications 86) depicted as correspondingdiscrete icons 488. Icons 488 include, for example, an Electronic Mail(E-Mail) icon 490, a Calendar icon 492, an Address Book icon 494, aTasks icon 496, a Messages icon 497, a MemoPad icon 498, and a Searchicon 499, respectively.

As shown in FIG. 5, memory 224 includes a plurality of applications orroutines 586 associated with the visually displayed icons 488 of FIG. 4for the processing of data. Applications 586 may be in any of a varietyof forms such as, without limitation, software, firmware, and the like.Applications 586 include, for example, an Electronic Mail (E-Mail)application 588 (FIG. 5) associated with E-mail icon 490 (FIG. 4), aCalendar application 590 (FIG. 5) associated with Calendar icon 492(FIG. 4), an Address Book application 592 (FIG. 5) associated withAddress Book icon 494 (FIG. 4), a Tasks application 594 (FIG. 5)associated with Tasks icon 496 (FIG. 4), a MemoPad (Memos) application596 (FIG. 5) associated with MemoPad icon 498, a Messages application598 (FIG. 5) associated with Message icon 497 (FIG. 4), and a Searchapplication 500 (FIG. 5) associated with Search icon 499 (FIG. 4). Anoperating system (OS) program 516 also resides in memory 224. The mobilestation of the present disclosure is also adapted to render visual mapsin its visual display, and utilizes a mapping application 550 stored inmemory 224 to facilitate map rendering and related functionality.

In FIG. 4, the “home” screen output is currently active and constitutesthe main “ribbon” application for displaying the icons 488 shown. Anapplication, such as E-mail application 588 of FIG. 5, may then beinitiated (opened or viewed) from user interface 402 by providing asuitable user input to it. For example, E-mail application 588 may beinitiated (opened or viewed) by rotating positioning wheel 410 tohighlight E-mail icon 490 and providing a selection input by translatingpositioning wheel 410 in the direction indicated by arrow 438. Asanother example, display 222 displays icon 499 associated with Searchapplication 500 and accepts input from positioning wheel 410 to initiatea search from that icon 499. Applications 586 may be additionally oralternatively initiated (opened or viewed) from user interface 402 byproviding another suitable input to it, such as by suitably rotating or“rolling” trackball 433 and providing a selection input by, for example,pushing the trackball 33 (e.g. somewhat similar to positioning wheel 410except into the plane of FIG. 4).

Movement, navigation, and/or scrolling with use of a cursor/viewpositioning mechanism is beneficial given the relatively large size ofvisually displayed information and the compact size of display 222, andsince information and messages are typically only partially presented inthe limited view of display 222 at any given moment. As previouslydescribed, positioning wheel 410 is one helpful cursor/view positioningmechanism to achieve such movement. Positioning wheel 312, which may bereferred to as a scrollwheel, specifically includes a circular discwhich is rotatable about a fixed axis of housing 302 and may be rotatedby the end user's index finger or thumb. When the information or messageis being partially displayed, an upwards rotation of positioning wheel410 causes an upwards scrolling such that display 222 presents viewingof an upper portion of the information or message. Similarly, adownwards rotation of positioning wheel 410 causes a downwards scrollingsuch that display 222 presents viewing of a lower portion of theinformation or message. Positioning wheel 410 is mounted along a fixedlinear axis such that the end user can depress positioning wheel 410inwards toward housing 406 (e.g. with the end user's index finger orthumb) for selection of information. Again, see the direction indicatedby an arrow 414 of positioning wheel 410 shown.

A more detailed mechanism for positioning wheel 410 is now described inrelation to FIGS. 6 and 7. Positioning wheel 410 of FIGS. 6-7 is shownconnected to and rotatable about a body assembly 610. Body assembly 610may be connected to or be part of a slide assembly 720. Slide assembly720 allows the entirety of positioning wheel 410 and body assembly 610may move freely laterally 414 with respect to the handheld device.Lateral positioning wheel movement 414 is defined as movement along aplane normal to the rotational axis of positioning wheel 410. To controlthis lateral movement 414, slide assembly 720 may be connected to acontrol mechanism such as a cam mechanism 730 with a cam 731, oralternatively a level mechanism, a solenoid mechanism, or some otheractuating means. Cam mechanism 730 is connected to a cam controller 740responsible for controlling a lateral position of positioning wheel 410.As cam 731 connected to cam mechanism 730 and slide assembly 720 moves,positioning wheel 410 and body assembly 610 accordingly move laterally.Such lateral movement inwards toward the housing is detectable by theprocessor of the mobile station as a switch input (actuation ordepression of the positioning wheel key).

Although positioning wheel 410 has been shown and described as onemechanism for use in navigating and moving through visually displayedinformation, any suitable mechanism may be utilized for the present userinterface techniques, such a trackball; UP, DOWN, LEFT, and RIGHT keys;a mouse and cursor mechanism; or a touch screen display mechanism.

FIG. 8 is a flowchart which helps describe a method of providing a maplocation in a user application using a Uniform Resource Location (URL)string. The method may be performed by a mobile station as described inrelation to the previous figures, or by any other computer orcommunication device (e.g. a PC). The steps of the method may beperformed by one or more processors of the device. A computer programproduct for the mobile station may include computer instructions storedon a computer readable medium (memory, a floppy disk or CD-ROM) whichare written in accordance with the described logic of this method.

Beginning at a start block 802 of FIG. 8, the processor causes a map tobe visually displayed in a display (step 804 of FIG. 8). Next, a userinput request to copy a location of the map is received through the userinterface (step 806 of FIG. 8). In response to the user input request,the processor produces a URL string corresponding to the location of themap (step 808 of FIG. 8). The URL string includes a server address andlatitude and longitude coordinates corresponding to the location of themap. Another parameter, such as a zoom parameter or a referencecoordinate or sizing parameter, may also be provided, although suchinformation may be implied or set by default as an alternative. Theserver address is an address to a server (preferably a public domainserver) which is operative to provide map data in response to a requestfor the map data using the URL string. Specifically, the URL string mayhave the following predetermined format for all such requests:

http://<server address> lat=<latitude coordinate>& Ion=<longitudecoordinate>& z=<zoom parameter>

Subsequently, the processor causes the URL string to be inserted in theelectronic file or message (step 810 of FIG. 8), preferably forcommunications to another communication device. The electronic file ormessage may be an e-mail file or message, a calendar file or message, atask file or message, or a map file or message, as examples. Steps 808and 810 may be triggered and performed automatically by the processor inresponse to the request in step 806 without further user intervention.Alternatively, step 806 may be a first user input request to invoke aCOPY function and step 810 performed in response to receiving a seconduser input request to invoke a PASTE function.

FIG. 9 is a flowchart which helps describe a method of utilizing the maplocation in the user application using the URL string. The method may beperformed by a mobile station as described in relation to the previousfigures, or by any other computer or communication device (e.g. a PC).The steps of the method may be performed by one or more processors ofthe device. A computer program product for the mobile station mayinclude computer instructions stored on a computer readable medium(memory, a floppy disk or CD-ROM) which are written in accordance withthe described logic of this method.

Beginning with a start block of step 902, an electronic file or messagewhich includes a uniform resource locator (URL) string is received bythe processor (step 904 of FIG. 9). The electronic file or message maybe an e-mail file or message, a calendar file or message, a task file ormessage, or a map file or message, as examples. The URL string includesa server address and latitude and longitude coordinates corresponding tothe location of the map. Another parameter, such as a zoom parameter ora reference coordinate or sizing parameter, may also be provided,although such information may be implied or set by default as analternative. The server address is an address to a server (preferably apublic domain server) which is operative to provide map data in responseto a request for the map data using the URL string. Specifically, again,the URL string may have the following format for all such locationrendering:

http://<server address>? lat=<latitude coordinate>& Ion=<longitudecoordinate>& z=<zoom parameter>

Next, a user input request to select the URL string in the electronicfile or message is received via the user interface from the end user(step 906 of FIG. 9).

In response to the user input request in step 906, the processor causesa map of a location corresponding to the latitude and longitudecoordinates to be visually displayed in the display (step 908 of FIG.9). Step 908 is preferably triggered and performed automatically by theprocessor in response to the request in step 906 without further userintervention. As will be described later below in relation to FIG. 44,processing of the received URL string may be handled differentlydepending on the type of device or whether a predetermined mappingapplication is installed in the device, so that mapping functionality isprovided in different environments.

In one scenario of step 908, when the device has the mapping applicationinstalled, the processor may first identify whether map datacorresponding to the map of the location is available in its memorycache from a previous rendering of the map. If the map data is availablein its cache, the processor selects this cached map data to render themap of the location. If the map data is not available in the cache,however, the processor must retrieve the map data from an externalsource. In this case, the user input request causes the processor to acton the URL string by sending a request message for the map data to theserver at the server address. The request message includes the latitudeand longitude coordinates (and any other information) to the server asinput parameters. A source address of the communication device is alsoreceived at the server along with the request. In response, the serveroperates to receive and process the request to retrieve map data for therendering of the map at the location corresponding to the latitude andlongitude coordinates. The server then operates to respond to therequest of the communication device by sending a response message whichincludes the map data to the communication device at its address. Theprocessor of the communication device receives the map data and causesthe map of the location to be visually displayed in the display.

Specific examples of the techniques of FIGS. 8 and 9 are now illustratedwith reference to FIGS. 10-43, for providing and utilizing map locationsin user applications with use of the URL strings.

FIGS. 10-14 are sequential views of display 222 to further illustratethe method of FIG. 8 in connection with an e-mail application (e.g.E-mail application 588 of FIG. 5). In FIG. 10, it is shown that a map1002 of a location at an indicated address 1004 of “450 March Road,Kanata, Ontario, Canada” is visually displayed in display 222. Inresponse to a depression or actuation of a positioning mechanism (e.g.positioning wheel 410 of FIGS. 4, 6, and 7) by the end user during thedisplay of map 1002, in FIG. 11 it is shown that a pop-up or pull-downlist or menu 1102 having a plurality of function identifiers 1104 isdisplayed over a portion of map 1002. The end user may subsequentlyrotate the positioning mechanism to scroll a cursor up/down throughfunction identifiers 1104 of menu 1102 for highlighting the same one ata time. In FIG. 11, it is shown that the cursor is positioned so as tohighlight an “E-mail Location” function 1106 in menu 1102. In responseto a depression or actuation of the positioning mechanism by the enduser while E-mail Location function 1106 is highlighted, in FIG. 12 itis shown that the processor causes a new e-mail message 1204 to becreated from the e-mail application and displayed in display 222. Newe-mail message 1202 is automatically populated with information in ane-mail message body 1202 of new e-mail message 1204. As shown, e-mailmessage body 1202 includes a map location indicia 1212 (“You havereceived a map location”) which prefaces a location URL string 1210 ofthe type previously described in relation to FIG. 8. Location URL string1210 corresponds to the location of map 1002 displayed in FIGS. 10 and11, and reads ashttp://bbplanet1.ottawa.testnet.rim.net?lat=45.34080&lon=-75.91429&z=3″.Message body space 1214 remains in e-mail message body 1202 for the enduser to input additional text for the new e-mail message 1202. Othere-mail message fields 1206, such as an e-mail “TO” field 1208, are leftblank for the end user to input text, whereas other e-mail messagefields, such as an e-mail “SUBJECT” field, may be pre-populated. In FIG.13, it is shown that the end user has used the input keys of the deviceto input a recipient e-mail address 1302 (for address bookcontact=“Richard Peillard”) into the TO field 1208. In response to adepression or actuation of the positioning mechanism by the end userduring the display of new e-mail message 1204, in FIG. 14 it is shownthat a pop-up or pull-down list or menu 1402 having a plurality offunction identifiers is displayed over a portion the new e-mail message.The end user may subsequently rotate the positioning mechanism to scrollthe cursor up/down through the function identifiers of menu 1402 forhighlighting the same one at a time. In FIG. 14, it is shown that thecursor is positioned so as to highlight a “Send” function identifier1404 in menu 1402. In response to a depression or actuation of thepositioning mechanism by the end user while Send function identifier1404 is highlighted, in FIG. 12 the processor causes new e-mail message1204 to be sent or communicated to the recipient e-mail address.

FIGS. 15-20 are sequential views of display 222 to further illustratethe method of FIG. 9 in connection with the e-mail application. In FIG.15, a message header list 1506 of received messages (e.g. e-mailmessages) is shown in a message header homescreen 1502. In this example,the message header list 1506 of received messages reveals a messageheader 1504 for a message received from “Ron Dicke.” In response to adepression or actuation of the positioning mechanism by the end userduring the highlighting of message header 1504, in FIG. 16 it is shownthat a pop-up or pull-down list or menu 1602 having a plurality offunction identifiers 1604 is displayed over a portion message headerhomescreen 1502. The end user may subsequently rotate the positioningmechanism to scroll the cursor up/down through the function identifiers1604 of menu 1602 for highlighting the same one at a time. In FIG. 16,it is shown that the cursor is positioned so as to highlight an “Open”function 1606 in menu 1602. In response to a depression or actuation ofthe positioning mechanism by the end user while Open function identifier1606 is highlighted, in FIG. 17 it is shown that the processor causes areceived e-mail message 1702 corresponding to message header 1504 to beopened and viewed in display 222. The e-mail message body includes a maplocation indicia 1704 (“You have received a map location”) whichprefaces a location URL string 1706 of the type previously described inrelation to FIG. 9. Location URL string 1706 corresponds to the locationof a map which may be displayed and reads ashttp://bbplanet1.ottawa.testnet.rim.net?lat=45.40003&lon=-75.73588&z=1.The end user may subsequently rotate the positioning mechanism to scrollthe cursor up/down through e-mail message 702 in FIG. 18 to select andhighlight 1802 the URL string 1706. In response to a depression oractuation of the positioning mechanism by the end user during thehighlighting or selection of URL string 1706, in FIG. 19 it is shownthat a pop-up or pull-down list or menu 1902 having a plurality offunction identifiers 1904 is displayed over a portion e-mail message1702. The end user may subsequently rotate the positioning mechanism toscroll the cursor up/down through the function identifiers 1904 of menu1902 for highlighting the same one at a time. In FIG. 19, it is shownthat the cursor is positioned so as to highlight a “View Map” functionidentifier 1906 in menu 1902. In response to a depression or actuationof the positioning mechanism by the end user while View Map functionidentifier 1906 is highlighted, in FIG. 20 it is shown that theprocessor causes a map 2002 of the location corresponding to the URLstring to be rendered in display 222. A location marker 2004 is alsoprovided in map 2002 at the exact location specified in the URL string.

FIGS. 21-24 are sequential views of display 222 to further illustratethe method of FIG. 8 in connection with any file or message using a COPYfunction and a PASTE function. In FIG. 21, it is shown that a map 2102of a location is visually displayed in display 222. In response to adepression or actuation of the positioning mechanism by the end userduring the display of map 2102, in FIG. 22 it is shown that a pop-up orpull-down list or menu 2202 having a plurality of function identifiers2204 is displayed over a portion of map 2102. The end user maysubsequently rotate the positioning mechanism to scroll the cursorup/down through function identifiers 2204 of menu 2202 for highlightingthe same one at a time. In FIG. 22, it is shown that the cursor ispositioned so as to highlight an “Copy Location” function identifier2206 in menu 2202. In response to a depression or actuation of thepositioning mechanism by the end user while Copy Location functionidentifier 2206 is highlighted, the processor causes a location URLstring of the type previously described in relation to FIG. 8 to beproduced and stored internally in memory into a “copy” buffer. The enduser may subsequently open any type of file or message and “paste” theURL string. In FIG. 23, it is shown that the end user has opened thee-mail application and caused a new e-mail message 2302 to be producedand displayed in display 222. The new e-mail message 2302 has aplurality of message fields 2304 as previously described. In response toa depression or actuation of the positioning mechanism by the end userduring the display of new e-mail message 2302, in FIG. 23 it is shownthat a pop-up or pull-down list or menu 2306 having a plurality offunction identifiers 2308 is displayed over a portion of new e-mailmessage 2302. The end user may subsequently rotate the positioningmechanism to scroll the cursor up/down through function identifiers 2308of menu 2310 for highlighting the same one at a time. In FIG. 23, it isshown that the cursor is positioned so as to highlight a “Paste”function identifier 2310 in menu 2306. In response to a depression oractuation of the positioning mechanism by the end user while Pastefunction identifier 2310 is highlighted, it FIG. 24 it is shown that theprocessor causes the previously-buffered URL string 2402 to be retrievedand copied into the e-mail message body of new e-mail message 2302. Thee-mail message body therefore includes URL string 2402 of the typepreviously described in relation to FIG. 8. URL string 2402 correspondsto the location of map 2102 displayed in FIGS. 21 and 22, and reads ashttp://bbplanet1.ottawa.testnet.rim.net?lat=45.34335&lon=-75.90660&z=3″.In response to a depression or actuation of the positioning mechanism bythe end user while a Send function identifier is highlighted, theprocessor causes new e-mail message 2303 to be sent or communicated tothe intended recipient.

FIGS. 25-29 are sequential views of display 222 to further illustratethe method of FIG. 9 in connection with the tasks application (e.g.tasks application 594 of FIG. 5). After the tasks application is openedor invoked, in FIG. 25 it is shown that a task header list 2502 for aplurality of tasks of the end user is displayed in display 222. In thisexample, a task item 2504 having a task item identifier 2506 of “Stop ByRIM Kanata” is found within task header list 2502. In response to adepression or actuation of the positioning mechanism by the end userwhile task item 2504 is highlighted, in FIG. 26 it is shown that theprocessor causes task item 2504 to be opened to display task information2602 for editing. FIG. 26 shows various task details 2604 associatedwith task 2602, including a location URL string 2602 of the typepreviously described in relation to FIG. 9. A cursor 2610 is shown inFIG. 26, which may be further positioned by the end user through taskdetails 2604, so as to highlight other information 2702 in task details2604 as shown in FIG. 2702. In particular, in FIG. 28 it is shown thatthe end user may rotate the positioning mechanism to scroll cursor 2802up/down through the task details 2604 for highlighting URL string 2602.In response to a depression or actuation of the positioning mechanism bythe end user during the highlighting of URL string 260, in FIG. 29 it isshown that a pop-up or pull-down list or menu 2902 having a plurality offunction identifiers 2904 is displayed over a portion of the task indisplay 222. The end user may subsequently rotate the positioningmechanism to scroll the cursor up/down through the function identifiers2904 of menu 2902 for highlighting the same one at a time. In FIG. 29,it is shown that the cursor is positioned so as to highlight a “ViewMap” function 2906 in menu 2902. In response to a depression oractuation of the positioning mechanism by the end user while View Mapfunction identifier 2906 is highlighted, the processor causes a map ofthe location indicated by URL string 2606 to be produced in the display.

FIGS. 30-34 are sequential views of display 222 to further illustratethe method of FIG. 9 in connection with a map or location application.After the location application is opened or invoked, in FIG. 30 it isshown that a location header list 3002 for a plurality of locations ofinterest to the end user is displayed in display 222. In this example, alocation item 3004 having a location identifier 3006 of “RIM's KanataOffice” is found within location header list 3002. In response to adepression or actuation of the positioning mechanism by the end userwhile location item 3004 is highlighted, in FIG. 31 it is shown that apop-up or pull-down list or menu 3102 having a plurality of functionidentifiers 3104 is displayed in a portion of display 222. The end usermay subsequently rotate the positioning mechanism to scroll the cursorup/down through the function identifiers 3104 of menu 3102 forhighlighting the same one at a time. In FIG. 31, it is shown that thecursor is positioned so as to highlight a “View” function 3106 in menu3102. In response to a depression or actuation of the positioningmechanism by the end user while View function identifier 3106 ishighlighted, the processor causes location item 3004 to be opened todisplay location information 3202 for viewing. Notably, FIG. 26 shows alocation URL string 3204 of the type previously described in relation toFIG. 9. In response to a depression or actuation of the positioningmechanism by the end user during the highlighting of URL string 3204, inFIG. 33 it is shown that a pop-up or pull-down list or menu 3302 havinga plurality of function identifiers 3304 is displayed in a portion ofdisplay 222. The end user may subsequently rotate the positioningmechanism to scroll the cursor up/down through the function identifiers3304 of menu 3302 for highlighting the same one at a time. In FIG. 33,it is shown that the cursor is positioned so as to highlight a “ViewMap” function 3306 in menu 3302. In response to a depression oractuation of the positioning mechanism by the end user while View Mapfunction identifier 3306 is highlighted, in FIG. 34 it is shown that theprocessor causes a map 3402 of the location indicated by the URL stringto be produced in the display. A location marker 3404 is also providedin map 3402 at the exact location specified by the URL string.

FIGS. 35-43 are sequential views of display 222 to further illustratethe method of FIG. 9 in connection with a calendar application (e.g.calendar application 590 of FIG. 5). After the calendar application isopened or invoked, in FIG. 35 it is shown that a calendar schedule 3502for a plurality of appointments or meetings 3504 for the end user isdisplayed in display 222. In this example, a calendar appointment item3506 having an appointment identifier 3510 for a “New Building Meeting”at around 10:00 AM on Mar. 17, 2006 is displayed. In response to adepression or actuation of the positioning mechanism by the end userwhile calendar appointment item 3506 is highlighted, in FIG. 36 it isshown that a pop-up or pull-down list or menu 3602 having a plurality offunction identifiers 3604 is displayed in a portion of display 222. Theend user may subsequently rotate the positioning mechanism to scroll thecursor up/down through the function identifiers 3604 of menu 3602 forhighlighting the same one at a time. In FIG. 36, it is shown that thecursor is positioned so as to highlight an “Open” function identifier3606 in menu 3602. In response to a depression or actuation of thepositioning mechanism by the end user while Open function identifier3606 in menu 3602 is highlighted, the processor causes calendarappointment item 3506 to be opened to display further appointmentinformation for viewing as shown in FIG. 37. The additional appointmentinformation in FIG. 37 more clearly reveals that the appointment detailsmay include a location URL string 3508 corresponding to the location ofthe meeting. URL string 3508 is of the type previously described inrelation to FIG. 9. FIG. 38 reveals that new calendar appointments 3802may be created with such URL strings 3508 being copied or insertedtherein, and saved as shown in FIG. 39 (see e.g. a menu 3902 of aplurality of function identifiers 3904 which include a “Save” functionidentifier 3906) and FIG. 40, and communicated or sent to othercommunication devices for scheduled calendar meetings. As shown in FIG.41, URL string 3508 in calendar appointment 3802 may be highlighted bythe end user with use of the positioning mechanism. In response to adepression or actuation of the positioning mechanism by the end userduring the highlighting of URL string 3508, in FIG. 42 it is shown thata pop-up or pull-down list or menu 4202 having a plurality of functionidentifiers 4204 is displayed over a portion of calendar appointment3802 in display 222. The end user may subsequently rotate thepositioning mechanism to scroll the cursor up/down through the functionidentifiers 4204 of menu 4202 for highlighting the same one at a time.In FIG. 42, it is shown that the cursor is positioned so as to highlighta “View Map” function 4206 in menu 4202. In response to a depression oractuation of the positioning mechanism by the end user while View Mapfunction identifier 4206 is highlighted, it is shown in FIG. 43 that theprocessor causes a map 4302 of the location indicated by the URL stringto be produced in display 222. A location marker 4304 is also providedin map 4302 at the exact location specified by the URL string.

FIG. 44 is a flowchart which describes a method for use in processingthe URL string for map display in accordance with the presentdisclosure. The method may be performed by a mobile station as describedin relation to the previous figures, or by any other computer orcommunication device (e.g. a PC). The steps of the method may beperformed by one or more processors of the device. Corresponding stepsof the method are performed by one or more servers in the communicationsystem. A computer program product may include computer instructionsstored on a computer readable medium (memory, a floppy disk or CD-ROM)which are written in accordance with the described logic of this method.

FIG. 45 depicts pertinent components of the communication system withinwhich the method of FIG. 44 may be performed. Reference numerals thatare the same as that shown and described in relation to FIG. 3A andelsewhere depict the same or like components. In addition, other networkaspects are explicitly shown in FIG. 45 including a computer orcommunication network such as the Internet 4502, a map coordinatingserver 4504 having one or more accessible databases 4506, and a publicmap server 4508 having one or more accessible databases 4510. Mapcoordinating server 4504 and public map server 4508 are publiclyaccessible or public servers. Public map server 4508 may be any suitablepublicly-accessible map server such as one provided by Yahoo, Expedia,Google, to name but a few. Preferably, public map server 4508 providesfor interactive map functionality.

In describing the method of FIG. 44, the steps of the flowchart may bereferred to in combination with components in FIG. 45. Beginning withthe flowchart of FIG. 44, a URL string of the type specified above isreceived in an electronic file or message at a computer device (step4402 of FIG. 44). For example, the URL string may be received inhypertext link format according to one of the methods describedpreviously in relation to FIG. 9, One example of the URL string isrevealed in the box in step 4402 of FIG. 44 (e.g.“bbplanet1.ottawa.testnet.rim.net/?lat=45.44328&lon=-75.69311&z=3”). TheURL string may be referred to more generally as a hypertext link mappingindicator since alternative indicators may be displayed in its place(e.g. icon or other graphics or text), with the actual URL string beinghidden. In this approach, the hypertext link mapping indicator or URLstring may be received at one of three different types of computerdevices: a computer device such as a personal computer (PC) (desktop orlaptop) or mobile communication device which has the predeterminedmapping application installed therein (e.g. in FIG. 45, mobilecommunication device 202 having mapping application 550 operating incarrier network 303); a mobile communication device of the same typeabove without the predetermined mapping application installed therein(e.g. in FIG. 45, a mobile communication device 4550 operating incarrier network 303); or a computer device such as a PC (desktop orlaptop) without the predetermined mapping application installed therein(e.g. in FIG. 45, a computer 4552 connected to the Internet 4502).

In response to an end user selection of the URL string via the userinterface, the computer device causes processing associated with the URLstring to occur for mapping the location specified in the URL string. Ifthe computer device that processes the URL string has the predeterminedmapping application installed as identified at step 4404 (e.g. thecomputer device is mobile device 202 having mapping application 550 inFIG. 45), then the technique for rending the map is performed with useof the installed mapping application as described earlier above (e.g.see FIGS. 3A-3B and FIG. 8), using map data from the device's cache orobtained from the network server/database as/when needed (step 4406 ofFIG. 44). Note that the predetermined mapping application (operating inconnection with the associated network server(s) as needed) is optimizedand preferred for use with this device in terms of memory usage andprocessing power and provides an interactive map interface. The computerdevice having the predetermined mapping application is adapted to makethe decision in step 4404 with use of a “URL hook” associated with theURL string which is registered when the mapping application is installedin the device. In response to the end user selection of the URL string,the computer device may identify all or a portion of the selected URLstring—e.g. “bbplanet1”—which triggers the mapping functionality in thedevice. Thus, in response to the end user selection of the URL stringfor this type of device, a mapping function of the mapping applicationinstalled in the device is invoked to render a map of the specifiedlocation in the URL string.

If the predetermined mapping application is not installed or provided inthe computer device as identified in step 4404 (e.g. the computer deviceis mobile device 4550 without having the predetermined mappingapplication in FIG. 45), however, then the processor causes a requestfor an HTML page to be sent to the server address of the serverspecified in the URL string (step 4408 of FIG. 44). The server ispreferably the map coordinating server 4504 in FIG. 45. In step 4408 ofthe flowchart, this process is indicated as “request index.php”. If thecomputer device has a predetermined browser type (e.g. mobile devicebrowser) or is a predetermined mobile device type (as tested in step4410 of FIG. 44 by the map coordinating server), then flow proceeds tostep 4412 of FIG. 44. In step 4412, the computer device (e.g. thepredetermined type of mobile device—not a PC or laptop computer)receives the HTML data from the map coordinating server and causes theHTML page which contains an image of the map to be displayed (step 4418of FIG. 44). Since the computer device may be a mobile communicationdevice having relatively limited processing power and memory capability,the map image is preferably a fixed image (e.g. a bitmap, such as afixed and non-interactive image) or other different type.

The image of the map may be obtained by the map coordinating serverthrough steps 4420 and 4422 of FIG. 44 now described. In steps 4420 and4422, responsive to the end user's request, the map coordinating servercauses a request for the map image to be sent to a server address of apublic map server (e.g. public map server 4508 of FIG. 45) (step 4420 ofFIG. 44) (“request device_map.php”). In response, a portable networkgraphics (PNG) image is created and obtained (step 4422 of FIG. 44).Specifically, a screen size is obtained using resource descriptionframework (RDF) identified in the URL string specified in a“HTTP_PROFILE” HTTP header of the request. A default screen size may beprovided as an alternative (e.g. defaulting to 234×320) if the header orresource is not available. Tile numbers are calculated based on therequested latitude and longitude coordinates (and zoom) and screen size.Tiles associated with these tile numbers are fetched from the public mapserver having the tiles stitched together, and assembled with otherinformation such as a location marker and copyright information etc.which are added. The generated image is returned to the requestingcomputer device by the map coordinating server and displayed in thedisplay of the computer device. Again, the map image displayed in steps4418, 4420, and 4422 is preferably not provided with an interactive mapinterface capability but rather merely a fixed image without end usermanipulation capability.

The HTML page displayed in step 4418 of FIG. 44 may further contain anddisplay a link (e.g. a hypertext link) to a server address of a downloadserver for downloading the mapping application. Thus, the mapcoordinating server may produce data to generate this link on the samepage as the map image for the mobile communication device. The downloadserver may or may not be the same server as the map coordinating server.The link may be or include an invitation to the end user to download thepredetermined mapping application. In response to an end user selectionof such link through the user interface, the mobile communication devicecauses a mapping application download page from the server at the serveraddress to be displayed. From there, a mapping application download fordownloading the predetermined mapping application to the computer devicemay be initiated in response to an end user selection of an associatedlink. Alternatively, the mapping application download for thepredetermined mapping application may be initiated in response to an enduser selection of the initial link which is contained and displayed onthe same HTML page as the map image.

Next, if the computer device fails to have the predetermined mobilebrowser type or is not the predetermined mobile device type identifiedin step 4410 of FIG. 44, then flow proceeds to steps 4414 and 4416 ofFIG. 44 for a computer device which is a desktop PC or laptop withrelatively larger memory and processing power. In this case, thecomputer device causes a request to be sent (step 4414) (“requestdesktop.php”) to the server address specified in the URL string (e.g.map coordinating server 4504 of FIG. 45) and an HTML page of a map isobtained and displayed at the communication device in response (step4416). Although the request was made to the map coordinating server, therequest was actually redirected to a public map server (e.g. public mapserver 4508 of FIG. 45) which provides for interactive mapping abilityand functionality (e.g. a Google Maps server associated with a GoogleMaps application). Thus, communication by the computer device with thisother predetermined server may be initiated through a redirection tothat server from the map coordinating server. The map of the location isprovided in the display of the computer device, where a JavaScriptApplication Programming Interface (API) may be provided (e.g. GoogleMaps JavaScript API), and the API may be used to display the locationmap and add a location marker. Thus, interactive map functionality isprovided for computer devices having suitable memory and processingpower capabilities.

Advantageously, processing of the received URL string may be handleddifferently depending on the type of device or whether a predeterminedmapping application is installed in the device, so that suitable oroptimized mapping functionality is provided in different types of deviceenvironments.

Thus, as described herein, a method for use in mapping a location in acomputer device includes the steps of receiving an electronic file ormessage which includes a hypertext link mapping indicator associatedwith a uniform resource locator (URL) string having a server address andlatitude and longitude coordinates; receiving, through a user interfaceof the computer device, an end user selection of the hypertext linkmapping indicator in the electronic file or message; and in response tothe end user selection of the hypertext link mapping indicator: if apredetermined type of mapping application is provided in the computerdevice, invoking a mapping function of the mapping application toproduce a map of a location corresponding to the latitude and longitudecoordinates for visual display in a display of the computer device (e.g.based on received maplet data); and if the predetermined type of mappingapplication type is not provided in the computer device, requesting andreceiving map data from a map coordinating server identified by theserver address of the URL string to produce a map of the location forvisual display in the display (e.g. based on a bitmap image). If thepredetermined type of mapping application is not provided in thecomputer device, and the computer device or associated browser isidentified as not being that of a mobile communication device (i.e. thecomputer device has higher processing capabilities), then the computerdevice causes a request to be sent to the map coordinating server at theserver address and, in response to the request, receives a redirectionfrom the map coordinating server to an interactive map server at aninteractive map server address and further requests and receives mapdata from the interactive map server at the interactive map serveraddress to produce a map of the location for visual display in thedisplay. Advantageously, processing of the received hypertext linkmapping indicator is handled differently depending on the type of deviceor whether a predetermined mapping application is installed in thedevice, so that optimal mapping functionality is provided for differentdevice environments.

The above-described embodiments of the present disclosure are intendedto be examples only. Those of skill in the art may effect alterations,modifications and variations to the particular embodiments withoutdeparting from the scope of the invention. The invention describedherein in the recited claims intends to cover and embrace all suitablechanges in technology.

What is claimed is:
 1. A method in a wireless communication device fordisplaying a map, the wireless communication device including a userinterface comprising a display, the method comprising: receiving amessage comprising a hypertext link object to a map location; displayingthe message comprising the hypertext link object; receiving, via theuser interface, a selection of the hypertext link object, the hypertextlink object being associated with a Uniform Resource Locator (URL)string which consists of a server address, location data correspondingto the map location, and map parameters; and in response to receivingthe selection of the hypertext link object, identifying a mappingapplication trigger within the server address; invoking the mappingapplication and displaying a map of the map location.
 2. The method ofclaim 1, wherein the mapping application trigger is a URL hookregistered on the device.
 3. The method of claim 2, wherein the URLstring is registered when the mapping application is installed on thedevice.
 4. The method of claim 1, wherein the hypertext link object isthe only link to the map location in the message.
 5. The method of claim3, wherein the hypertext link object is the only link to the maplocation in the message.
 6. A non-transitory computer readable mediumcomprising instructions in code which when stored in a memory of awireless communication device and executed by a processor of thewireless communication device causes the wireless communication deviceto: receive a message comprising a hypertext link object to a maplocation; display the message comprising the hypertext link object;receive, via the user interface, a selection of the hypertext linkobject, the hypertext link object being associated with a UniformResource Locator (URL) string which consists of a server address,location data corresponding to the map location, and map parameters; andin response to receiving the selection of the hypertext link object,identify a mapping application trigger within the server address; invokethe mapping application and display a map of the map location.
 7. Thecomputer readable medium of claim 6, wherein the mapping applicationtrigger is a URL hook registered on the device.
 8. The computer readablemedium of claim 7, wherein the URL string is registered when the mappingapplication is installed on the device.
 9. The computer readable mediumof claim 6, wherein the hypertext link object is the only link to themap location in the message.
 10. The computer readable medium of claim8, wherein the hypertext link object is the only link to the maplocation in the message.
 11. A wireless communication device comprising:a processor; a wireless transceiver coupled to the processor; a memorycoupled to the processor; a user interface comprising a display; theprocessor being configured to: receive a message comprising a hypertextlink object to a map location; display the message comprising thehypertext link object; receive, via the user interface, a selection ofthe hypertext link object, the hypertext link object being associatedwith a Uniform Resource Locator (URL) string which consists of a serveraddress, location data corresponding to the map location, and mapparameters; and in response to receiving the selection of the hypertextlink object, identify a mapping application trigger within the serveraddress; invoke the mapping application and display a map of the maplocation.
 12. The wireless communication device of claim 11, wherein themapping application trigger is a URL hook registered on the device. 13.The wireless communication device of claim 12, wherein the URL string isregistered when the mapping application is installed on the device. 14.The wireless communication device of claim 11, wherein the hypertextlink object is the only link to the map location in the message.
 15. Thewireless communication device of claim 13, wherein the hypertext linkobject is the only link to the map location in the message.